Remotely initiating lost mode on a computing device

ABSTRACT

Systems, methods, and non-transitory computer-readable storage media are provided for remotely initiating lost mode on a computing device. A request that lost mode be initiated can include a message and contact information provided by the requesting user. Once authenticated, a command to initiate lost mode is sent to the lost device. Initiating lost mode includes locking the lost device and suppressing select functionality. The message and contact information are displayed and the lost device is enabled to contact the requesting user using the contact information. The lost device can also collect and transmit location data to the requesting user. The location data can be presented on a map indicating the lost devices location and the time the lost device was at the location. The location data can be scheduled to be resent to the user based on numerous factors such as a set schedule, rules or heuristic.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part (CIP) of U.S. patentapplication Ser. No. 13/488,438, filed on Jun. 4, 2012; this applicationalso claims the benefit of U.S. Provisional Patent Application No.61/657,855, filed on Jun. 10, 2012, entitled “REMOTELY INITIATING LOSTMODE ON A COMPUTING DEVICE”; both of which are hereby expresslyincorporated herein by reference in their entireties.

BACKGROUND

1. Technical Field

The present disclosure relates to computing devices and, morespecifically, to remotely initiating a lost mode on a computing device.

2. Introduction

Modern advances in computing devices have resulted in smaller, morepowerful and wirelessly networked computing devices that can be easilycarried by users at all times. As a result, these devices are relied ongreatly by their owners and often are trusted to carry their owner'spersonal and sensitive information. Consequently, the great power,portability and convenience of these devices must be balanced againstthe potential for substantial financial damage to the owner in the eventthat a device becomes lost or stolen.

Naturally, theft of such devices has increased as thieves are attractedto the high price and high demand for such computing devices as well asthe possibility of stealing personal information of the owner of thecomputing device. The high price and demand of a computing device canalso tempt a non-thief that finds a lost computing device to keep thedevice rather than search for its rightful owner. Alternatively, aperson that finds a lost device and intends to return it may find itdifficult to locate the owner.

Current systems attempt to address these problems by providing thelocation of the device to an owner of a lost device by sending GPS orother locational tracking information to a secure website to which theowner may login. However, these types of systems do not help a personthat finds the lost device return it to its owner. Other systems allowthe lost device to be locked to deter theft. Although effective, thelock also makes it even more difficult for a person that finds thedevice to determine is the identity of the owner of the device becausethe information on the device cannot be accessed. Leaving the deviceunlocked increases the likelihood that the identity of the owner can beascertained, however it also increases the likelihood that the devicewill not be returned and leaves personal or sensitive data stored on thelost device unprotected. Accordingly, there is a need for an improvedsystem for locating a lost computing device that allows the owner of thecomputing device to protect the personal or sensitive data on thecomputing device while also making it easy for a person that finds thecomputing device to return the computing device to its owner.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for remotely initiating lost mode on a computing device. Arequesting user can request that lost mode be initiated on a lostcomputing device. The request can be made on a requesting device innetwork communication with a server configured to communicate with thelost device. The request can include request data such as a message,contact information and password. The request data can be provided bythe requesting user when requesting that lost mode be initiated on thelost device. A requesting user can be required to enter authenticatinginformation to ensure that the requesting user is authorized to requestthat lost mode be initiated on the lost device.

Upon a request being made by a requesting user and the requesting userbeing authenticated, the server can be configured to send a command,including the request data, to the lost device to initiate lost mode onthe lost device. Initiating lost mode can include locking the lostdevice and suppressing select functionality of the lost device so thatthe functionality of the lost device as well as data and applicationsstored on the lost device cannot be accessed by an unauthorized user.

Further, the ability to turn off the lost device can be suppressed. Insome embodiments, the lost device can be configured to act as though itis powering down upon receiving an input command to power off the lostdevice, but in actuality the device remains running, thus misleading apotential thief about the status of the lost device.

Additionally, the message and contact information provided by therequesting user can be displayed on the user device to alert an honestperson who finds the lost device as to how to contact the owner. A userinterface element, such as a button, can also be presented andconfigured to enable the lost device to contact the requesting user byusing the provided contact information. For example, a lost device suchas a smart phone can be enabled to make an outbound call to a phonenumber provided by a requesting user as their contact information, whileoutbound calls to all other numbers are restricted. A person who findsthe phone can thus easily contact the requesting user while all otherfunctionality of the lost device is suppressed, and data stored thereonare protected.

In some embodiments, the device can be silently locked so that apotential thief is not alerted that lost mode has been initiated on thelost device. This can include presenting the lost device as being lockedwithout presenting a message or contact information. In someembodiments, silently locking the device can include presenting the lostdevice as being in a powered off or inoperative state, rather thanlocked.

When lost mode is initiated, the lost device can also be configured tocollect and transmit location data identifying the location of the lostdevice to the requesting user. The location data can be presented on amap indicating the location of the lost device as well as the time thatthe lost device was at the displayed location. Further status data, suchas the remaining battery life of the lost device or whether lost modehas been initiated on the lost device can also be transmitted with thelocation data. The location data can be scheduled to be transmitted tothe user based on numerous factors such as a set schedule, rules orheuristics.

If the lost device is unavailable when the requesting user requests thatlost mode be initiated on the lost device, the server can keep checkingthe status of the lost device until the lost device is available andthen send the command for lost mode to be initiated on the lost device.Further, a message alerting the requesting user that the lost device isavailable and that lost mode has been initiated can be sent to therequesting user either by the server or by the lost device.

In some embodiments, a message can be sent to the requesting user upon adetermination that the lost device has been “found.” Upon lost modebeing initiated on the lost device, the lost device can be configured tosend a notification to the requesting user upon a status changeoccurring which indicates that the lost device is in the possession ofanother person. For example, the status change can occur upon thelocation of the lost device changing or an input on the lost devicebeing engaged.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features of the disclosure can be obtained, a moreparticular description of the principles briefly described above will berendered by reference to specific embodiments thereof, which areillustrated in the appended drawings. Understanding that these drawingsdepict only exemplary embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 illustrates an exemplary system embodiment;

FIG. 2 illustrates an exemplary embodiment of a general purposecomputing environment wherein a user can remotely initiate lost mode ona user device;

FIG. 3 illustrates an exemplary method embodiment of remotely initiatinglost mode on a lost device;

FIG. 4 illustrates an exemplary method embodiment of initiating lostmode on the lost device;

FIG. 5 illustrates an exemplary method embodiment of transmittinginformation data to the requesting user;

FIG. 6 illustrates a screenshot of an exemplary interface configured toauthenticate a requesting user;

FIG. 7 illustrates a screenshot of an exemplary interface configured toreceive a password from the requesting user;

FIG. 8 illustrates a screenshot of an exemplary interface wherein arequesting user can enter contact information;

FIG. 9 illustrates a screenshot of exemplary embodiment of an interfacewherein a requesting user can enter a message;

FIG. 10 illustrates a screenshot of an exemplary embodiment of a lostdevice after lost mode has been initiated;

FIG. 11 illustrates a screenshot of an exemplary embodiment of a lostdevice after lost mode has been initiated;

FIG. 12 illustrates a screenshot of an exemplary embodiment of locationdata being presented;

FIG. 13 illustrates a screenshot of an exemplary embodiment of locationdata being presented;

FIG. 14 illustrates an exemplary embodiment of location data beingpresented to the requesting user;

FIG. 15 illustrates a screenshot of an exemplary embodiment of lost modewherein only a message is presented;

FIG. 16 illustrates a screenshot of an exemplary embodiment of lost modewherein the requesting user did not provide a message;

FIG. 17 illustrates a screenshot of an exemplary embodiment of a lostdevice that is locked using a silent lock;

FIG. 18 illustrates an exemplary embodiment of a method of initiatinglost mode on a lost device that is not available;

FIG. 19 illustrates an exemplary method embodiment of determining that alost device has been found by another person; and

FIG. 20 illustrates an exemplary method embodiment of initiating lostmode wherein the functionality to power off the lost device issuppressed.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

With reference to FIG. 1, an exemplary system 100 includes ageneral-purpose computing device 100, including a processing unit (CPUor processor) 120 and a system bus 110 that couples various systemcomponents including the system memory 130 such as read only memory(ROM) 140 and random access memory (RAM) 150 to the processor 120. Thesystem 100 can include a cache 122 of high speed memory connecteddirectly with, in close proximity to, or integrated as part of theprocessor 120. The system 100 copies data from the memory 130 and/or thestorage device 160 to the cache 122 for quick access by the processor120. In this way, the cache 122 provides a performance boost that avoidsprocessor 120 delays while waiting for data. These and other modules cancontrol or be configured to control the processor 120 to perform variousactions. Other system memory 130 may be available for use as well. Thememory 130 can include multiple different types of memory with differentperformance characteristics. It can be appreciated that the disclosuremay operate on a computing device 100 with more than one processor 120or on a group or cluster of computing devices networked together toprovide greater processing capability. The processor 120 can include anygeneral purpose processor and a hardware module or software module, suchas module 1 162, module 2 164, and module 3 166 stored in storage device160, configured to control the processor 120 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 120 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

The system bus 110 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. A basicinput/output (BIOS) stored in ROM 140 or the like, may provide the basicroutine that helps to transfer information between elements within thecomputing device 100, such as during start-up. The computing device 100further includes storage devices 160 such as a hard disk drive, amagnetic disk drive, an optical disk drive, tape drive or the like. Thestorage device 160 can include software modules 162, 164, 166 forcontrolling the processor 120. Other hardware or software modules arecontemplated. The storage device 160 is connected to the system bus 110by a drive interface. The drives and the associated computer readablestorage media provide nonvolatile storage of computer readableinstructions, data structures, program modules and other data for thecomputing device 100. In one aspect, a hardware module that performs aparticular function includes the software component stored in anon-transitory computer-readable medium in connection with the necessaryhardware components, such as the processor 120, bus 110, output device170, and so forth, to carry out the function. The basic components areknown to those of skill in the art and appropriate variations arecontemplated depending on the type of device, such as whether the device100 is a small, handheld computing device, a desktop computer, or acomputer server.

Although the exemplary embodiment described herein employs a storagedevice 160, it should be appreciated by those skilled in the art thatother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, digital versatile disks, cartridges, random access memories(RAMs) 150, read only memory (ROM) 140, a cable or wireless signalcontaining a bit stream and the like, may also be used in the exemplaryoperating environment. Non-transitory computer-readable storage mediaexpressly exclude media such as energy, carrier signals, electromagneticwaves, and signals per se.

To enable user interaction with the computing device 100, an inputdevice 190 represents any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 170 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems enable a user to provide multiple types of input to communicatewith the computing device 100. The communications interface 180generally governs and manages the user input and system output. There isno restriction on operating on any particular hardware arrangement andtherefore the basic features here may easily be substituted for improvedhardware or firmware arrangements as they are developed.

For clarity of explanation, the illustrative system embodiment ispresented as including individual functional blocks including functionalblocks labeled as a “processor” or processor 120. The functions theseblocks represent may be provided through the use of either shared ordedicated hardware, including, but not limited to, hardware capable ofexecuting software and hardware, such as a processor 120, that ispurpose-built to operate as an equivalent to software executing on ageneral purpose processor. For example the functions of one or moreprocessors presented in FIG. 1 may be provided by a single sharedprocessor or multiple processors. (Use of the term “processor” shouldnot be construed to refer exclusively to hardware capable of executingsoftware.) Illustrative embodiments may include microprocessor and/ordigital signal processor (DSP) hardware, read-only memory (ROM) 140 forstoring software performing the operations discussed below, and randomaccess memory (RAM) 150 for storing results. Very large scaleintegration (VLSI) hardware embodiments, as well as custom VLSIcircuitry in combination with a general purpose DSP circuit, may also beprovided.

The logical operations of the various embodiments are implemented as:(1) a sequence of computer implemented steps, operations, or proceduresrunning on a programmable circuit within a general use computer, (2) asequence of computer implemented steps, operations, or proceduresrunning on a specific-use programmable circuit; and/or (3)interconnected machine modules or program engines within theprogrammable circuits. The system 100 shown in FIG. 1 can practice allor part of the recited methods, can be a part of the recited systems,and/or can operate according to instructions in the recitednon-transitory computer-readable storage media. Such logical operationscan be implemented as modules configured to control the processor 120 toperform particular functions according to the programming of the module.For example, FIG. 1 illustrates three modules Mod1 162, Mod2 164 andMod3 166 which are modules configured to control the processor 120.These modules may be stored on the storage device 160 and loaded intoRAM 150 or memory 130 at runtime or may be stored as would be known inthe art in other computer-readable memory locations.

Having disclosed some components of a computing system, the disclosurenow turns to FIG. 2, which illustrates a general purpose computingenvironment 200 wherein a user can remotely initiate lost mode on a userdevice. As illustrated, multiple computing devices can be connected to acommunication network and be configured to communicate with each otherthrough use of the communication network. The communication network 210can be any type of network, including a local area network (“LAN”), suchas an intranet, a wide area network (“WAN”), such as the internet, orany combination thereof. Further, the communication network 210 can be apublic network, a private network, or a combination thereof. Thecommunication network can also be implemented using any type or types ofphysical media, including wired communication paths and wirelesscommunication paths associated with one or more service providers.Additionally, the communication network 210 can be configured to supportthe transmission of messages formatted using a variety of protocols.

Multiple computing devices can be connected to the communicationnetwork. A computing device can be any type of general computing devicecapable of network communication with other computing devices. Forexample, the computing device can be a personal computing device such asa desktop or workstation, a business server, or a portable computingdevice, such as a laptop, smart phone, or a post-pc device. Thecomputing device can include some or all of the features, components,and peripherals of computing device 100 of FIG. 1. To facilitatecommunication with other computing devices, the computing device canalso include a communication interface configured to receive acommunication, such as a request, data, etc., from another computingdevice in network communication with the computing device and pass thecommunication along to an appropriate module running on the computingdevice. The communication interface can also be configured to send acommunication to another computing device in network communication withthe computing device.

As illustrated in FIG. 2, the exemplary system includes three computingdevices in network communication with each other: a lost user device205, a Find My Device (FMD) server 215 and a requesting user device 220.The system illustrated in FIG. 2 can be configured to remotely initiatelost mode on the lost user device 205. The requesting user device 220can be configured to communicate with the FMD server 215 to create arequest to initiate lost mode on the lost device 205.

The FMD server 215 can be configured to receive a request to initiatelost mode on the lost user device 205 and to send a command to the lostuser device 205 to initiate lost mode. As illustrated, the FMD server215 can contain a number of components. The components can include oneor more databases for storing data relevant to the operation of the FMDserver 215, e.g. an account database 225 and a location database 230;and one or more modules or interfaces for interacting with the databasesand/or controlling the features provided by the FMD server 215, e.g., anauthentication module 235, a request module 240 and a location module245. Each of these components is discussed in more detail below,however, it should be understood to one skilled in the art that theconfiguration illustrated is simply one possible configuration and thatother configurations, with more or less components, are possible.

The FMD server 215 can include an account database 225 configured tostore a user profile for each of a plurality of users. A user's profilecan include a variety of information about the user, for example theinformation can include a user name, password, a list of all computingdevices owned by the user, an identifier for each computing device ownedby the user, user specified preferences, contact information,demographic information, etc.

The FMD server 215 can also include an authentication module 235,configured to communicate with the account database 225 and authenticatethe user requesting to initiate lost mode on the lost user device 205 sothat the request will be accepted. To properly authenticate a requestinguser, the authentication module 235 can be configured to prompt therequesting user to enter authenticating information, such as a user nameand password, or other predetermined information. To confirm that theauthenticating information received from the requesting user is correct,the authentication module 235 can be configured to communicate with theaccount database 225 to confirm that the given user name and passwordmatch a user profile in the account database 225. If the given user nameand password matches a user profile stored in the account database 225,the requesting user can be authenticated as having permission to requestthat lost mode be initiated on any of the computing devices associatedwith the user's profile. Although user name and password are used as anexample, one skilled in the art will recognize that any variety ofauthenticating information can be requested from the user, includingpersonal information or answers to predetermined security questions.

The FMD server 215 can also include a request module 240 configured toallow a user to request that lost mode be initiated on the lost userdevice 205. The request module 240 can be configured to provide therequesting user with an interface to create the request that lost modebe initiated on the lost user device 205. The interface can also beconfigured to receive request data from the requesting user. Forexample, request data can include an identifier identifying the lostuser device. The identifier can be any type of identifier which canidentify the lost user device. For example, if the lost user device 205is a smart phone, the identifier can include a phone number associatedwith the device. Alternatively, the identifier can include a unique nameor ID associated with the device. In some embodiments, an authenticatedrequesting user can be presented with a list of all user devices listedin the user's profile, and the requesting user can select which userdevice is lost.

In addition to the identifier, the request data can also include contactinformation. Contact information can include any type of informationused to contact the requesting user. For example, contact informationcan include a phone number, e-mail address, physical address, instantmessenger handle, website, etc. The request module 240 can be configuredto prompt the requesting user for the contact information. In someembodiments, the request module 240 can be configured to use informationspecified in a user's profile data as the contact information. In someembodiments, the request module 240 can be configured to ask arequesting user whether the requesting user would like to use thecontact information stored in the user's profile or enter new contactinformation.

The request data can also include a message specified by the requestinguser. The message can be any message specified by the requesting user,which the requesting user would like to have displayed on the lostdevice 205. In some embodiments, the message can be predetermined andstored in the user's profile and the request module 240 can beconfigured to allow the requesting user to either use the stored messageor create a new one.

The request data can also include a password. The password can be anytype of password known to those skilled in the art such as a numericpin, alphanumeric character password, gesture, etc. In some embodiments,the password can be preset by the requesting user and the request module240 can be configured to allow the requesting user to either use thepreset password or enter a new one.

The requesting user can access the FMD server 215 to request that lostmode be initiated on the lost device 205 by using the requesting device220 to communicate with the FMD server 215. For example, in someembodiments, the requesting device 220 can include a web browserapplication configured to request access to the FMD server 215 via thecommunication network 210. In some embodiments, the authenticationmodule 235 and request module 240, either entirely or partially can berunning on the requesting device 220 and the requesting user can accessthe modules 235 240 from the requesting device 220 to create therequest.

Upon receiving the request, including request data, from the requestinguser and authenticating that the requesting user is authorized toinitiate lost mode on the lost device 205, the request module 240 can beconfigured to send a command via a telecommunications network, includingthe received request data, to the lost device 205 to initiate lost mode.The lost device 205 can be configured to initiate lock mode on the lostdevice 205 upon receiving the command.

The FMD server 215 can also include a location module 245 configured toreceive location data from the lost device 205 and to transmit thelocation to the requesting user. The location data can include dataindicating the location of the lost device 205 as well as the time thelost device 205 was at that location. The location module 245 can beconfigured to transmit the location data to the requesting user innumerous ways. For example, in some embodiments, the location data canbe sent to the requesting device 220. The location module 245 candetermine whether the requesting device 220 is available, and ifavailable, send the location date. If the requesting device 220 is notavailable, the location module can be configured to store the locationdata in a location database 230 on the FMD server 215 until therequesting device 220 is available. Alternatively, the location data maybe sent to an email address of the requesting owner, either stored inthe owner's profile or specified by the requesting owner during therequest to initiate lost mode.

In some embodiments, the amount of location data stored in the locationdatabase 230 can be limited for privacy concerns. For example, thelocation data stored can be limited to only the most recent location ofthe lost device 205 and, upon receiving new location data, thepreviously stored location data can be erased from the location database230. In some embodiments, the location data stored in the locationdatabase 230 can be erased after a specified time if not sent to therequesting user. For example, the location module 245 can be configuredto erase any location data stored in the location database 230 after 24hours. In some embodiments, the location data is erased after thelocation data is transmitted to the requesting user.

The location data can be presented to the requesting user in numerousways. In some embodiments, the location data can be presented to therequesting user on a map that tracks the movement of the lost device205. In some embodiments, the location data can be presented to therequesting user by giving the street address or GPS coordinates of thelost device 205.

The location data can also be sent to the requesting user in numerousways. For example, in some embodiments the requesting user can log in toa web interface or application configured to communicate with thelocation module 245 to view the location of the lost device. In someembodiments, the location data can be e-mailed to the owner of the userdevice. In some embodiments, the location data can be sent to therequesting device 220 via a push notification to immediately update therequesting user of the location of the lost device 205.

Although the above examples of sending location data are described,these examples are not meant to be limiting and are just a few possibleembodiments. One skilled in the art would recognize that there arenumerous ways to send and present data.

The lost device 205 can contain a number of components. The componentscan include one or more databases for storing data relevant to theoperation of the device, e.g., location database 250, and one or moremodules or interfaces for interacting with the databases and/orcontrolling the features provided by the lost user device, e.g., a userinterface module 255, lost mode module 260, and Find My Device (FMD)module 265. Each of these components is discussed in more detail below,however, it should be understood to one skilled in the art that theconfiguration illustrated is simply one possible configuration and thatother configurations, with more or less components, are possible.

The lost device 205 can include a user interface module 255 configuredto manage the user interface on the lost device 205. This can includedisplaying all user interface elements on the device such as icons,buttons, controls, date, time, notifications, alerts, etc., as well asthe background, wallpaper, clock, etc.

The lost device 205 can also include a FMD module 265 configured toinitiate lost mode on the lost device 205 upon receiving the command toinitiate lost mode from the FMD server 215. For example, in someembodiments, the FMD module 265 can be a daemon running in thebackground on the lost device 205 and configured to communicate with theoperating system to initiate applications and modules running on thelost device 205 as well control hardware components of the lost device205.

The FMD module 265 can be configured to receive the command from the FMDserver 215 to initiate lost mode on the lost device 205. Upon receivingthe command, the FMD module 265 can be configured to execute the lostmode module 260. Further, the FMD module 265 can be configured tocommunicate the request data received from the FMD server 215 to thelost mode module 260.

The lost mode module 260 can be configured to run with or as part of theuser interface module 255 to graphically lock the lost device 205 and,in some embodiments, require a password to unlock the phone.

In some embodiments, the lost mode module 260 can be a plug-inapplication configured to communicate with the user interface module 255through use of an Application Programming Interface (API) provided bythe user interface module 255. The lost mode module 260 can beconfigured to instruct the user interface module 255 to lock the lostdevice 205 and to suppress functionality of the lost device 205. Forexample, the lost mode module 260 can instruct the user interface module255 that certain user interface elements are not to be displayed on thelost device 205. For example, the lost mode module 260 can instruct theuser interface module 255 to suppress all user interface elements thatwould allow access to data and/or applications on the lost device 205.Further, the lost mode module 260 can instruct the user interface module255 to suppress other features such as presenting notifications on thelost device 205. Although presenting notifications is suppressed, thelost device 205 can still be enabled to receive data which wouldnormally trigger the notification being presented.

In some embodiments, the lost mode module 260 can suppress functionalitythat associates a stored contact name with an incoming communication.For example, while in lost mode, a lost device 205 such as a smart phonecan remain enabled to receive incoming phone calls so that, for example,a requesting user can contact the lost device 205. The lost device 205can have contact data, such as a contact name, associated with thecontact number so that, when receiving a call from the contact number,the contact name is presented on the lost device 205 rather than thecontact number. The lost mode module 260 can suppress this functionalityto protect the contact name from being viewed by an unauthorized user.In some embodiments, the contact number will be displayed rather thanthe associated contact name. In some embodiments, both the contact nameand the contact number can be protected and a message indicating onlythat an incoming call is being received can be displayed.

In some embodiments, the lost mode module 260 can be configured tosuppress the functionality to manually power off the lost device 205.This can protect the device from a potential thief powering off the lostdevice 205 to prevent the lost device 205 from transmitting locationdata describing the location of the lost device 205 and thus beingtracked. In some embodiments, the lost mode module 260 can be configuredto cause the lost device 205 to appear as if though it is powering off,while the lost device 205 in actuality remains powered on. For example,the lost mode module 260 can be configured to present a display thatimitates the lost device 205 turning off and being in an off state uponreceiving an input to manually turn off the lost device 205. This canfool a potential thief into believing that the lost device 205 is turnedoff and thus that the location of the lost device 205 cannot be tracked.

In some embodiments, the lost mode module 260 can instruct the userinterface module 255 to suppress any set display preferences such as abackground or wallpaper. For example, the lost mode module 260 can beconfigured to instruct the user interface module 255 to display only aplain standard background such as a plain grey background.

The lost mode module 260 can also instruct the user interface module 255to present the contact information and message received from the FMDserver 215. In some embodiments, the lost mode module 260 can beconfigured to vary its display based on whether a message and contactinformation has been specified by the requesting user. For example, if arequesting user does not enter contact information, the lost mode modulecan 260 be configured to display only the message, or vice versa, onlythe contact information if the requesting user did not enter a message.

In some embodiments, the lost mode module 260 can be configured todisplay a default message or contact information if either is notspecified by the requesting user. For example, if the requesting useronly specifies contact information, a default message such as “Pleasecontact me at this number” can be displayed. Alternatively, if therequesting user only specifies a message, the lost mode module 260 canbe configured to display a known contact for the requesting user. Forexample, if the lost device 205 is a tablet PC, the lost mode module candisplay an e-mail address associated with an e-mail application on thelost device.

In some embodiments, the lost mode module 260 can be configured todisplay a default message and contact information if neither is suppliedby the requesting user. In some embodiments, if the requesting user doesnot specify a message or contact information, the lost mode module 260can be configured to silently lock the lost device 205 so that it doesnot appear that lost mode has been initiated on the lost device 205. Forexample, the lost device 205 can appear to be locked and require apassword as though the lost device 205 was previously configured torequire a password rather than having been remotely locked. In someembodiments, silently locking the lost device 205 can includeconfiguring the lost device 205 to appear as if though it is poweredoff, inoperative, unresponsive, etc. In addition to presenting thecontact information, the lost mode module 260 can also be configured toinstruct the user interface module 255 to present a user interfaceelement on the lost device 205 that is enabled with the limitedfunctionality to allow the lost device 205 to contact the requestinguser using the contact information. For example, if the lost device 205is a smart phone and the provided contact information is a phone number,the lost mode module 260 can be configured to instruct the userinterface module 255 to present the contact number and provide a userinterface element which enables the smart phone the limitedfunctionality of making outbound phone calls to the provided contactnumber, while outbound calls to all other numbers are prohibited. Thus,if the smart phone is found, an honest person can easily contact theowner of the device by simply selecting the user interface element to beconnected to the provided contact number. Alternatively, the contactinformation can be an e-mail address and the user interface element canallow the user to compose and send an e-mail to the owner of the deviceat the e-mail address provided.

In addition to executing the lost mode module 260, in some embodiments,the FMD module 265 can also be configured to transmit location data tothe requesting user. For example, the FMD module 265 can be configuredto collect location data from a GPS component of the lost device 205 andperiodically send the location data to the requesting user. The locationdata can be any type of data that can identify the location of the lostdevice. For example, the location data can be GPS coordinates, a streetaddress, etc. In addition, the location data can include the time thatthe lost device was at the specified location. For example, the FMDmodule 265 can be configured to receive the time from an internal clockrunning on the lost device 205.

In some embodiments, the FMD module 265 can be configured to gather thelocation data from a location database 250 on the lost device 205. Thelocation database 250 can be configured to store location data and atime associated with the location data. In some embodiments, thelocation database 250 can be configured to delete location data after apredetermined time. For example, to limit the amount of data storedabout a user and protect privacy, the location data can be deleted after24 hours and thus the location database 250 will only contain locationdata identifying where the lost device 205 has been for the previous 24hour period.

In some embodiments, the location data can include further status datasuch as the remaining battery life of the lost device 205 or whetherlost mode has been initiated on the lost device 205. Any status data canbe transmitted with the location data to the requesting user.

In some embodiments, the FMD module 265 can be configured to send thelocation data to the FMD server 215 which then sends the location datato the requesting user. In some embodiments, the FMD module 265 sendsthe location data to the requesting device 220. In some embodiments, theFMD module determines whether the requesting device 220 is available toreceive the location data, and if so, send the location data to therequesting device 220, but if the requesting device is not available,the FMD module 265 sends the location data to the FMD server 215. Insome embodiments, the FMD module 265 sends the location data to apersonal account associated with the requesting user, such as therequesting user's e-mail account. Although the above examples of sendinglocation data to a requesting user are described, these are justpossible embodiment and are not meant to be limiting. One skilled in theart would recognize that the location information can be sent to therequesting user in numerous other ways.

The FMD module 265 can be configured to schedule transmission of thelocation data in numerous ways. For example, in some embodiments, theFMD module 265 can be configured to send the location data in set timeintervals such as every 10 minutes, 30 minutes, 1 hour, etc. In someembodiments, the location data can be sent based on a heuristic thatdetermines when the requesting user would want the location data sent.For example, the heuristic can conclude that based on the lost device205 making a significant movement in location, the requesting user wouldwant to be updated of the new location of the lost device 205.

In some embodiments, the FMD module 265 can query the location of thelost device 205 on a set schedule to determine whether the lost device205 has made a significant movement. In some embodiments, the lostdevice 205 can offer functionality that can notify the FMD module 265when the lost device 205 has made a significant movement, such asthrough an API.

Alternatively, in some embodiments, the heuristic can determine that therequesting user would like to be updated about the location of the lostdevice based on the time of day, for example first thing in the morningwhen the requesting user is likely waking up. In some embodiments, theheuristic can determine that the requesting user would like to beupdated about the location of the device upon the lost device 205regaining network connection. For example, the lost device 205 might betransported to an area where network connection is unavailable. The FMDmodule 265 can be configured to send the location data to the requestinguser immediately upon the lost device 205 regaining network connection.

In some embodiments, the heuristic can determine that the requestinguser would want messages sent less frequently, for example when thebattery is running low and sending location data less frequently willpreserve the battery life and enable the lost device 205 to be trackedas long as possible. In some embodiments, the location data can betransmitted based upon a combination of a schedule and a heuristic. Forexample, location data can be transmitted every hour, but only if thelost device 205 has made a significant movement. The above examples areonly some possible embodiments and are not meant to be limiting. Oneskilled in the art would recognize that the location data can bescheduled for transmission in numerous ways known to those of ordinaryskill in the art.

In addition to transmitting location data, the FMD module 265 can alsobe configured to transmit other pertinent information to the requestinguser. For example, the remaining battery life can be transmitted to therequesting user. This can be sent and presented with the location dataso that the requesting user can be informed of the remaining batterylife of the lost device 205 at the time it was at the location.Alternatively, updates regarding the remaining battery life can betransmitted to the requesting user at predetermined milestones, such as20% battery life remaining or 10% battery life remaining.

In some embodiments, the remaining battery life can be presented as anestimation of how much time is remaining until the lost device 205 runsout of battery life and updates regarding the remaining battery life canbe transmitted to the requesting user at milestones based upon theamount of time remaining until the lost device runs out of power. Forexample, an update can be sent notifying the requesting user that thelost device 205 will run out of battery power in 10 minutes.

The remaining amount time until the battery runs out of power can beestimated in numerous ways. For example, the remaining amount of timeuntil the lost device 205 runs out of battery life can be estimatedbased in the current live power consumption rate of the lost device 205.In some embodiments, the remaining amount of time until the lost deviceruns out of battery life can be estimated based on historical dataconsumption of the lost device. Although the above examples are given,they are only some possible embodiments and not meant to be limiting.One of ordinary skill in the art would recognize that the remainingamount of time until the lost device 205 runs out of battery life can beestimated in any number of ways known in the art.

In some embodiments, the FMD module 265 can be configured to send statusdata to the requesting device 220. For example, the FMD module 265 cansend a notification to the requesting user upon the lost device 205being “found”. For example, the notification can be sent immediatelyupon a status change occurring on the lost device that indicates thatthe lost device is in the possession of a person. For example, thestatus change can occur upon a first action being taken on the lostdevice 205 or a first movement being detected by the lost device 205after lost mode has been initiated. Thus, the requesting user canascertain whether the lost device is in the possession of another personor if it is still lost.

In some embodiments, the FMD module 265 can be configured to proactivelyattempt to connect to available network connections. For example, a lostdevice 205 such as a laptop or tablet PC that does not have a mobilenetwork connection, can be configured to repeatedly check whetherwireless connections (e.g., WLAN, Bluetooth, etc.) are available andattempt to connect to any unprotected networks so that location dataupdates or other information can be sent to the requesting user.

To terminate lost mode on the lost device 205, the lost mode module 260can be configured to instruct the user interface module 255 to present aprompt for a password to be entered. If the proper password is entered,the FMD module can be configured to terminate the lost mode module 260,thus returning the user interface module 255 to its regularfunctionality. The lost device 205 can be unlocked and all suppressedfunctionality can be restored. Further, the FMD module 265 can stopcollecting and sending location data to the requesting user.

In some embodiments, lost mode can be terminated remotely. For example,the lost device 205 can receive a command from the requesting user thatlost mode be terminated. The command can include the password or requirethe password be entered prior to being sent. In some embodiments, thecommand can be received from the FMD server 215. In some embodiments,the command can be received from the requesting device 220.

FIG. 3 illustrates an exemplary method embodiment of remotely initiatinglost mode on a lost device. As illustrated, the method begins with arequest being received by the server to initiate lost mode on a lostdevice 305. The request can inform the server that the lost device islost and that the requesting user would like to initiate lost mode onthe lost device. Additionally, the request can include request data suchas a device identifier, contact information, message and password. Thedevice identifier can be any type of data that can identify the lostdevice such as a phone number, UUID, device name, etc.

The request data can also include contact information and a messageprovided by the requesting user to be displayed on the lost device. Thecontact information can be any information identifying how therequesting user can be contacted. For example, the contact informationcan be a phone number and be accompanied with the message, “Please callthis number if found.” Alternatively, the contact information can be ane-mail address and be accompanied with the message, “Please e-mail me atthis address if you find this device.”

In some embodiments, the request data can also include a password. Forexample, the requesting user can set a password that, upon lost modebeing initiated on the lost device, can be used to terminate lost modeand return the lost device to regular functionality.

The requesting user can request that lost mode be initiated on the lostdevice in numerous ways. For example, in some embodiments, therequesting user can log into a website configured to prompt a requestinguser for request data and send a request that lost mode be initiated onthe lost device. In some embodiments, the requesting user can use anapplication running on a requesting device in network communication withthe server to request that lost mode be initiated on the lost device.The application can be configured to prompt the user for request dataused to create the request.

Upon receiving the request at the server, the method continues to block310 where the server determines whether the requesting user isauthorized to initiate lost mode on the lost device. To accomplish this,the server can require that the requesting user enter authenticationinformation. For example, the requesting user can be prompted to enter auser name and password associated with the lost device. Alternatively,the requesting user can be prompted to answer predeterminedauthentication questions. For example, the authentication questions canask for personal information associated with the known owner of the lostdevice such as the owner's social security number, or mother's maidenname, etc.

If it is determined that the requesting user is not authorized toinitiate lost mode on the lost device, the method can proceed to block315 wherein the server sends the requesting user a message that therequesting user is not authorized to initiate lost mode on the lostdevice and the method ends.

If it is determined that the requesting user is authorized to initiatelost mode on the lost device, the method continues to block 320 whereina command is sent to the lost device instructing the lost device toinitiate lost mode. The command can include the request data received inthe request to initiate lost mode, such as the contact info, message,password, etc. An exemplary method of lost mode being initiated by thelost device is illustrated in FIG. 4 and explained in detail below.

The method illustrated in FIG. 3 then determines whether location datais received from the lost device 325. Location data can be any type ofdata that describes the location of the lost device. For example,location data can include the global positioning system (GPS)coordinates of the lost device or the street address of the lost device.

If no location data is received from the lost device, the method ends.If location data is received, the server can send the location data tothe requesting user 330.

FIG. 4 illustrates an exemplary method embodiment of initiating lostmode on the lost device. As illustrated the method begins at block 405when a command is received at the lost device to initiate lost mode. Thecommand can be received from a server that has authenticated therequesting user as being authorized to request that lost mode beinitiated on the lost device. The command can include request data suchas contact information, a message and a password.

After receiving the command, the method then continues to block 410wherein the lost device locks itself from use. For example, this caninclude presenting a lock screen that is void of any UI elements thatprovide access to functionality of the lost device or any data orapplications stored on the user device. In some embodiments, the lockscreen can prompt a user to enter a password that will unlock thedevice. In some embodiments, the lost device can be silently locked sothat a potential thief is not alerted to the fact that lost mode hasbeen initiated on the lost device.

In some embodiments, the lost device can also be locked so that datastored on the lost device cannot be accessed from another computingdevice connected to lost device. For example, if the lost device is asmart phone connected to a desktop computer, the smart phone can belocked so that the files stored on the smart phone cannot be accessed bythe desktop computer. Locking the lost device can protect the lostdevice and the data stored thereon from being accessed by anunauthorized user.

Upon locking the lost device, the method next suppresses selectfunctionality 415 of the lost device. This can include functionalitythat enables use of the lost device or presents information meant forthe owner of the lost device. For example, functionality such asnotifications and alerts displayed on the lost device can be suppressedso that information intended for the owner of the lost device cannot beviewed by an unauthorized user. In some embodiments, functionality thatdisplays a stored contact name associated with contact information issuppressed to protect the stored contact name from being viewed by anunauthorized user. For example, a contact name associates with anincoming phone number is not displayed when receiving a communicationfrom the incoming phone number. In some embodiments, any externalbuttons of the lost device can be suppressed to prevent the user fromaccessing functionality of the lost device.

In some embodiments, the functionality to turn the lost device off canbe suppressed to prevent a thief from prohibiting the lost device fromsending location information. In some embodiments, the lost device canbe configured to appear as if though it is powering off while it remainspowered on, thus fooling a potential thief about the current state ofthe device and not alarming the thief to the possibility that the lostdevice is being tracked.

Further functionality that can be can suppressed can include outgoingcalls, voice command functionality, camera, video camera, microphone,power, etc. Although only the above examples are given, they are only afew possible embodiments and are not meant to be limiting. One skilledin the art would recognize that any functionality of the lost device canbe suppressed.

Once the lost device is locked 410 and functionality is suppressed 415,the method continues to block 420 wherein the lost device transmitslocation data to the requesting user. The location data can be any datathat identifies the location of the lost device. For example, thelocation data can be the GPS coordinates of the lost device.

FIG. 5 illustrates an exemplary method embodiment of transmittinginformation data to the requesting user. As illustrated the methodbegins by collecting location data and the time 505 the location datawas collected. For example, the lost terminal can include a GPS devicecapable of communicating with a GPS satellite to receive the GPScoordinates of the lost device. The lost device can collect the locationdata directly from the GPS device. Alternatively, in some embodiments,the GPS device can periodically store the location data in a database onthe lost device and the location can be collected from the database. Thetime the location data was collected can be gathered from an internalclock running on the lost device. In some embodiments, the time can bereceived from the GPS satellite when the location GPS coordinates of thelost device are received from the satellite.

After collecting the location data and the associated time, the methoddetermines whether the requesting device is available 510 to receive thelocation data. The requesting device can be available if the requestingdevice is in a state that allows data to be received at the requestingdevice from the lost device. For example, in some embodiments therequesting device is available if the requesting device is in networkcommunication with the lost device. In some embodiments, the requestingdevice is available if the requesting device is logged into or runningan application configured to receive and present the location data. Ifthe requesting device is available, the lost device can transmit thelocation data to the requesting device 515. If the requesting deice isnot available, the lost device can transmit the location data to theserver 520 where it can be stored until the requesting device isavailable or until the requesting device accesses it from the server.

After the location data has been transmitted, the method can determinewhether a transmission condition has been triggered 525. A transmissioncondition can be a condition that, when met, instructs the lost deviceto transmit the location data to the requesting user. In someembodiments, the transmission condition can be triggered upon apredetermined amount of time passing since the last time location datawas transmitted. For example the transmission condition can be triggeredupon an hour passing from the last time location data was transmitted.

In some embodiments, the transmission condition can be triggered uponthe lost device making a significant change in location from the lasttransmitted location. For example, if the transmission condition can betriggered if the lost device travels a mile or more from the previouslytransmitted location.

The examples given of when a transmission condition can be triggered arejust example embodiments and not meant to be limiting. One of ordinaryskill in the art would recognize that the disclosed system can beconfigured in any way know in the art.

If it is determined that a transmission condition has been triggered,the method can return to block 505. If a transmission condition is nottriggered, the method can end.

Returning to FIG. 4, upon transmitting the location data, the method canthen continue to block 425 wherein the contact information and themessage are displayed on the lost device. For example, the contactinformation can be a phone number associated with the requesting userand the message can state “please call this number if you find thisdevice.” This allows a Good Samaritan who finds the lost device to beable to easily contact the requesting user.

The method can also display a user interface element 430 that, ifselected 435, enables the lost device to contact the requesting user atthe given contact information 440. For example, if the lost device is acellular phone and the contact information is a telephone number, a userinterface element can be displayed on the lost device that, uponselection, enables the lost device to make an outbound call to the phonenumber specified as the contact information. This allows an honestperson to easily contact the requesting user to contact from the lostdevice itself by simply pressing a single button. Although the userinterface element is configured to enable suppressed functionality, suchas making an outbound call, the enabled functionality can be limited tothe given contact information. For example, a lost smart phone can beenabled to only make a call to the phone number provided by therequesting user.

A requesting user can choose to terminate lost mode on the lost deviceby entering a password. The method can determine whether the passwordhas been entered 445, and if so terminate lost mode 450. Terminatinglost mode can include removing the lock on the lost device and restoringall suppressed functionality of the lost device. In some embodiments,the password can be entered on the lost device itself. In someembodiments, the password can be entered remotely, for example on arequesting device in communication with the server, and a command thatthe password has been entered can be sent to the lost device.

FIG. 6 illustrates a screenshot of an exemplary interface configured toauthenticate a requesting user. As illustrated, a requesting user can beprompted to enter a user name 605 and password 610 into the interface. Asign in button 615 can also be presented and configured to, uponselection, submit the requesting user's entered user name 605 andpassword 610. The submitted user name and password can be compared torecords in a user database to authenticate the requesting user. If theprovided user name 605 and password 610 are a match with the storedrecords, the requesting user can be authenticated.

FIG. 7 illustrates a screenshot of an exemplary interface configured toreceive a password from the requesting user. As illustrated, therequesting user can enter the password using the keypad provided. Insome embodiments, this interface can be configured to receive apredetermined password to authenticate a requesting user. In someembodiments, the interface can be configured to receive a new passwordfrom an already authenticated requesting user. The new password can beused to unlock the lost device after lost mode has been initiated on thelost device.

FIG. 8 illustrates a screenshot of an exemplary interface wherein arequesting user can enter contact information. The contact informationcan be included as part of a request to initiate lost mode on a lostdevice. The contact information can be displayed on the lost device sothat, if found, the requesting user can be contacted. As illustrated,the requesting user can enter contact information 805, such as a phonenumber, using a provided keypad 810. The user interface can also includea next button 815 configured to receive the contact information 805entered by the requesting user and direct the user to the interfaceillustrated in FIG. 9.

FIG. 9 illustrates a screenshot of an exemplary embodiment of aninterface wherein a requesting user can enter a message. The message canbe included as part of a request to initiate lost mode on a lost device.The message can be displayed on the lost device upon lost mode beinginitiated. As illustrated, the interface can provide the user with amessage input field 905 configured to receive the message from therequesting user. Although not illustrated, a requesting user can enterthe message using a keyboard or other input device. The interface canalso include a done button 910 that is configured to complete therequest to initiate lost mode on the lost device. Upon selection of thedone button, the entered message as well as any other request data suchas a password and contact information, can be assembled into a requestto initiate lost mode on a lost device and sent to the server.Alternatively, the done button can automatically send a command directlyto the lost device to initiate lost mode using the included requestdata.

FIG. 10 illustrates a screenshot of an exemplary embodiment of a lostdevice after lost mode has been initiated. As illustrated, the lostdevice has been locked and is void of all user interface elements thatwould allow access to functionality of the lost device or data orapplications stored on the user device. The lost device can display themessage 1005 alerting any person who finds the lost device that it hasbeen lost and to please call the requesting user. Further, therequesting user's contact information 1010 can also be displayed. Theillustrated embodiment also allows a user to enter a password which, ifentered correctly, unlocks the lost device and terminates lost mode,thus restoring the lost device to its regular function state.

FIG. 11 illustrates a screenshot of a different exemplary embodiment ofa lost device after lost mode has been initiated. Similar to theembodiment illustrated in FIG. 10, the lost device can be locked and themessage 1105 and contact information 1110 can be displayed to alert anyperson that finds the lost device that the device is lost and to pleasecontact the requesting user.

Additionally, a user interface element 1115 can be included whichenables the lost device to contact the requesting user using the contactinformation. As illustrated, the user interface element can be a buttontitle “Tap here to Call Owner” which is configured to contact therequesting user upon selection. While the user interface element isconfigured to allow the lost device make an outbound call to the givencontact information phone number, outbound calls cannot be made to anyother phone numbers, nor is any other locked or suppressed functionalityenabled.

This embodiment also includes a slide to unlock button 1120 rather thanthe password interface 1015 of FIG. 10. This is just another possibleembodiment and the slide to unlock button 1120 can be configured tobring up another page wherein the user is prompted to enter a passwordto unlock the lost device.

FIG. 12 illustrates a screenshot of an exemplary embodiment of locationdata being presented. As illustrated, the location data 1205 can bepresented as a dot over a map to illustrate the location of the device.Further, an info box 1210 can be presented with the dot that displaysthe time the location data was collected. As illustrated, the lostdevice was determined to be at the identified location one minute priorto the location data being presented. In some embodiments, the info box1210 can display other information such as the remaining battery life ofthe lost device at the time the lost device was at the location.

FIG. 13 illustrates a screenshot of an exemplary embodiment of locationdata being presented. As illustrated multiple location data points 13051310 1315 1320 can be displayed as dots on a map to illustrate themovement of the lost device. The location data points can be connectedby a line to display the path of the lost device and the dots can bedifferent colors to signify which location data point is the mostrecent. For example, all previous location data points can beillustrated in one color, such as green, while the most current datalocation point can be illustrate in a different color, such as red.Further, each location data point can be configured to display aninformation box 1325 associated with the location data point thatidentifies the time at which the device was at the given location datapoint. As illustrated, the lost device was at location data point 131516 minutes prior at 11:30 am.

In some embodiments, the presentation of multiple location data pointscan be concatenated or merged based upon the perspective at which themap is presented. For example, if the lost device travels a longdistance, such as from San Francisco, Calif. to New York, N.Y., alllocation data points presented in San Francisco can be presented as onepoint when viewing a map displaying the entire path of the lost device.This can result in the path of the lost device being displayed in asimpler form expressing only the major movements of the lost device andremoving confusing clutter of having multiple location data pointsdisplayed closely together.

If multiple location data points are merged into one location data pointthe time associated with the merged one location data point can be thelatest recorded time the lost device was at any of the merged locationdata points that have been merged into the one location data point. Forexample, if the lost device was last determined to be in San Franciscoat 4pm before leaving to New York, the one location data pointrepresenting the merged data points from the lost device being in SanFrancisco can be associated with the time 4pm because it is the lasttime associated with any of the merged location data points from thelost device being in San Francisco. Alternatively, the time associatedwith the one merged location data point can be represented as the spanof time starting with the earliest time associated with one of themerged location data points through the latest time associated with oneof the merged location data points. For example, if the earliestlocation data point merged into the one location data point representingthat the lost device was in San Francisco occurred at 11am, the time11am-4pm can be associated with the one location data point representingthe lost device being in San Francisco.

The merged location data points can be unmerged and displayed asindividual location data points for a more accurate view of the path ofthe lost device upon the requesting user zooming into the area of themap where the location data points have been merged. Thus, if therequesting user zoomed in to the map view of San Francisco, all themerged data points received from 11am-4pm can be presented separately sothat the requesting user can view the path the lost device traveledduring that period of time.

FIG. 14 illustrates an exemplary embodiment of location data beingpresented to the requesting user. As illustrated, three location datapoints 1415 are presented on a map interface and connected by lines toillustrate the path of the lost device. In addition to the location datapoints, the interface can also display other status data regarding thelost device. For example, as illustrated, status data that the lostdevice is locked and the locations are being tracked 1405 is presentedto the requesting user. Further, the remaining battery life of the lostdevice can be presented as an icon 1410 of a battery. In someembodiments, the remaining battery life can be presented as an amount ofremaining time until the lost device runs out of battery power. Asillustrated the lost device currently has full battery power.

FIG. 15 illustrates a screenshot of an exemplary embodiment of lost modewherein only a message is presented. As illustrated, a message 1505 ispresented to the requesting user; however contact information is notpresented. This can be because the requesting user did not includecontact information or chose to have only the message displayed.

FIG. 16 illustrates a screenshot of an exemplary embodiment of lost modewherein the requesting user did not provide a message. As illustratedthe provided contact information 1610 is displayed as well as a defaultmessage 1605. In some embodiments, no message can be included ratherthan a default message.

FIG. 17 illustrates a screenshot of an exemplary embodiment of a lostdevice that is locked using a silent lock. As illustrated, no message,contact information, or any other indication that lost mode has beeninitiated is displayed on the lost device. In some embodiments, the lostdevice can be configured to be unresponsive to input, thus appearing asif the lost device is malfunctioning rather than in lost mode. In someembodiments, initiating a silent lock locks the lost device so that apassword is required, although the lost device was not configured torequire a password prior to lost mode being initiated. The lost devicethus can appear to have always required the password to be unlockedrather than having been remotely placed into lost mode.

FIG. 18 illustrates an exemplary embodiment of a method of initiatinglost mode on a lost device that isn't available. As illustrated, themethod begins with a request to initiate lost mode on the lost devicebeing received at the server 1805. The method next determines whetherthe lost device is available 1810 to receive a communication from theserver. For example, the server can ping the lost device to determinewhether the lost device is currently in network communication with theserver. In some embodiments, the server can regularly receive statusdata from the lost device indicating that the lost device is currentlyconnected to a network and in network connection with the server, andbased on whether the status data has been received; determine whetherthe lost device is available.

If it is determined the lost device is not available, the methodcontinues to check whether the lost device is available. For example,the server can be configured to check the status of the lost device atregular time intervals. In some embodiments, the server can beconfigured to recheck the status of the lost device until it isdetermined that the lost device is available. In some embodiments, theserver can recheck whether the lost device is available until apredetermined time limit has expired upon which a failure notificationis sent to the requesting user and the method ends.

If it is determined that the lost device is available, the server cansend a command to the lost device 1815 to initiate lost mode on the lostdevice, preferably after authenticating the requesting user. The methodnext sends a notification to the requesting user 1820 that the lostdevice is available and that lost mode has been initiated on the lostdevice. In some embodiments, the notification can be sent by the server.In some embodiments, the notification can be sent by the lost device.

FIG. 19 illustrates an exemplary method embodiment of determining that alost device has been found by another person. As illustrated, the methodbegins at block 1905 when a command to initiate lost mode is received atthe lost device. Upon receiving the command the lost device initiateslost mode on the lost device.

At block 1915 the lost device determines whether a status changeindicating that the lost device has been found by another personoccurred. For example, a lost device might be lost when lost mode isinitiated, meaning that it is not in any person's possession but ratherlaying hidden or unfound. Upon lost mode being initiated, the lostdevice can begin to monitor for any indications that the lost device isin the possession of another person. For example, a determination thatthe location of the device has changed can be an indication that thelost device has been found by another person. Another indication that astatus of the lost device has changed can be a button or feature of thelost device being pressed or activated. In some embodiments, a lostdevice can include a tilt sensor and the status can change can be thetilt of the lost device changing.

If a status change has been detected that indicates that the lost devicehas been found by another person, the lost device can send anotification to the requesting user 1920 that the lost device has beenfound.

FIG. 20 illustrates an exemplary method embodiment of initiating lostmode wherein the functionality to power off the lost device issuppressed. As illustrated, the method begins with the lost device beinglocked 2005. The method next suppresses functionality of the lost device2010 including the ability of the lost device to be manually poweredoff. This can include suppressing any way the device can selectively bepowered off such as suppressing a power button on the lost device.

The method next transmits location data 2015 to the requesting user. Thelocation data can be any data indicating the location of the lostdevice.

The method next determines whether an input is received to manuallypower off the lost device manually 2020. For example, a potential thiefaware that lost mode has been initiated on the lost device can attemptto power off the lost device in order to prevent the lost device fromtransmitting additional location data. Although this functionality issuppressed, a potential thief aware that location data is still beingtransmitted from the lost device can take further steps to avoid beingcaught. For example, the potential thief may physically disable thedevice by opening the device or breaking the device. Alternatively, thepotential thief may travel a far distance or to an area that the thiefknows to be without network connection.

To avoid a potential thief taking such actions, upon receiving an inputto power off the lost device, the lost device visually “powers off”2025. This can include putting a display of the lost device into acondition wherein the display appears as if the lost device has beenpowered off. This can include replicating the visual interface anddisplay that would be presented when the lost device is normally poweredoff and results in the lost device appearing to be powered off. This caninclude suppressing other functionality of the lost device such asdisabling buttons to replicate the responsiveness of the lost devicewhen powered off. Although appearing to be powered off, otherfunctionality of the lost device such as sending and receiving datatransmissions, continue to be performed without any visual or audibleindications.

For example, a potential thief can push a power button on the lostdevice and the lost device can be configured to visually execute exactlyas it would if lost mode was not initiated. This can include presentinga graphical display or video as well as turning off any lights on thelost device. The lost device would react no differently than when lostmode is not initiated on the lost device and it is manually powered off.Visually “powering off” the lost device results in the lost deviceappearing and reacting exactly as if it would if it was actually poweredoff, although the lost device remains powered on and remains capable ofperforming certain functionality such as transmitting location data tothe requesting user.

Accordingly, at block 2030, the lost device determines whether atransmission trigger has been triggered and, if so, transmits locationdata to the requesting user 2035, while the lost device appears to bepowered off to the potential thief.

The present disclosure recognizes that the use of such personalinformation data in the present technology can be used to the benefit ofusers. For example, the personal information data can be used to betterunderstand user behavior, facilitate and measure the effectiveness ofadvertisements, applications, and delivered content. Accordingly, use ofsuch personal information data enables calculated control of thedelivered content. For example, the system can reduce the number oftimes a user receives a given ad or other content and can thereby selectand deliver content that is more meaningful to users. Such changes insystem behavior improve the user experience. Further, other uses forpersonal information data that benefit the user are also contemplated bythe present disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data should implement andconsistently use privacy policies and practices that are generallyrecognized as meeting or exceeding industry or governmental requirementsfor maintaining personal information data private and secure. Forexample, personal information from users should be collected forlegitimate and reasonable uses of the entity and not shared or soldoutside of those legitimate uses. Further, such collection should occuronly after the informed consent of the users. Additionally, suchentities would take any needed steps for safeguarding and securingaccess to such personal information data and ensuring that others withaccess to the personal information data adhere to their privacy andsecurity policies and procedures. Further, such entities can subjectthemselves to evaluation by third parties to certify their adherence towidely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for advertisement delivery services. In yetanother example, users can configure their devices or user terminals toprevent storage or use of cookies and other mechanisms from whichpersonal information data can be discerned. The present disclosure alsocontemplates that other methods or technologies may exist for blockingaccess to their personal information data.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

Embodiments within the scope of the present disclosure may also includetangible and/or non-transitory computer-readable storage media forcarrying or having computer-executable instructions or data structuresstored thereon. Such non-transitory computer-readable storage media canbe any available media that can be accessed by a general purpose orspecial purpose computer, including the functional design of any specialpurpose processor as discussed above. By way of example, and notlimitation, such non-transitory computer-readable media can include RAM,ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storageor other magnetic storage devices, or any other medium which can be usedto carry or store desired program code means in the form ofcomputer-executable instructions, data structures, or processor chipdesign. When information is transferred or provided over a network oranother communications connection (either hardwired, wireless, orcombination thereof) to a computer, the computer properly views theconnection as a computer-readable medium. Thus, any such connection isproperly termed a computer-readable medium. Combinations of the aboveshould also be included within the scope of the computer-readable media.

Computer-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing device to perform a certain function orgroup of functions. Computer-executable instructions also includeprogram modules that are executed by computers in stand-alone or networkenvironments. Generally, program modules include routines, programs,components, data structures, objects, and the functions inherent in thedesign of special-purpose processors, etc. that perform particular tasksor implement particular abstract data types. Computer-executableinstructions, associated data structures, and program modules representexamples of the program code means for executing steps of the methodsdisclosed herein. The particular sequence of such executableinstructions or associated data structures represents examples ofcorresponding acts for implementing the functions described in suchsteps.

Those of skill in the art will appreciate that other embodiments of thedisclosure may be practiced in network computing environments with manytypes of computer system configurations, including personal computers,hand-held devices, multi-processor systems, microprocessor-based orprogrammable consumer electronics, network PCs, minicomputers, mainframecomputers, and the like. Embodiments may also be practiced indistributed computing environments where tasks are performed by localand remote processing devices that are linked (either by hardwiredlinks, wireless links, or by a combination thereof) through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote memory storage devices.

The various embodiments described above are provided by way ofillustration only and should not be construed to limit the scope of thedisclosure. Those skilled in the art will readily recognize variousmodifications and changes that may be made to the principles describedherein without following the example embodiments and applicationsillustrated and described herein, and without departing from the spiritand scope of the disclosure.

We claim:
 1. A method, comprising: authenticating a requesting useroperating a requesting computing device to initiate a lost mode on acomputing device, where the authenticating is performed over acommunications network coupled to the requesting computing device andthe computing device; sending a first command over the communicationsnetwork to the computing device to initiate the lost mode on thecomputing device, where the lost mode includes locking the computingdevice or suppressing select functionality of the computing device;receiving, over the communications network, status data from thecomputing device, wherein the status data indicates at least a remainingbattery life associated with the computing device; presenting the statusdata of the computing device on the requesting computing device, whereinthe status data includes an estimated amount of remaining time until thecomputing device runs out of battery life; and sending a second commandto the computing device to send status data less frequently based on thestatus data indicating the remaining battery life of the computingdevice.
 2. The method of claim 1, wherein the status data includeslocation data identifying the location of the computing device and isassociated with a time indicating when the status data was gathered fromthe computing device.
 3. The method of claim 1, wherein the status datais transmitted upon the remaining battery life associated with thecomputing device reaching a predetermined milestone.
 4. The method ofclaim 3, wherein the milestone is the remaining battery life reaching apredetermined percentage of total battery life.
 5. The method of claim3, wherein the milestone is the remaining battery life reaching apredetermined amount of remaining time left until the computing deviceruns out of battery life.
 6. A system, comprising: one or moreprocessors; and memory containing instructions that, when executed bythe one or more processors, causes the one or more processors to performoperations comprising: authenticating a requesting user operating arequesting computing device to initiate a lost mode on a computingdevice, where the authenticating is performed over a communicationsnetwork coupled to the requesting computing device and the computingdevice; sending a first command over the communications network to thecomputing device to initiate the lost mode on the computing device,where the lost mode includes locking the computing device or suppressingselect functionality of the computing device; receiving, over thecommunications network, status data from the computing device, whereinthe status data indicates at least a remaining battery life associatedwith the computing device; presenting the status data of the computingdevice on the requesting computing device, wherein the status dataincludes an estimated amount of remaining time until the computingdevice runs out of battery life; and sending a second command to thecomputing device to send status data less frequently based on the statusdata indicating the remaining battery life of the computing device. 7.The system of claim 6, wherein the status data includes location dataidentifying the location of the computing device and is associated witha time indicating when the status data was gathered from the computingdevice.
 8. The system of claim 6, wherein the status data is transmittedupon the remaining battery life associated with the computing devicereaching a predetermined milestone.
 9. The system of claim 8, whereinthe milestone is the remaining battery life reaching a predeterminedpercentage of total battery life.
 10. The system of claim 8, wherein themilestone is the remaining battery life reaching a predetermined amountof remaining time left until the computing device runs out of batterylife.
 11. A method comprising: receiving, by a computing device, a firstcommand over a communications network to initiate a lost mode on thecomputing device; locking the computing device or suppressing selectfunctionality of the computing device; determining a remaining batterylife of the computing device; and sending, over the communicationsnetwork, status data indicating at least a remaining battery life of thecomputing device, wherein the status data includes an estimated amountof remaining time until the computing device runs out of battery life;and receiving, by the computing device, a second command over thecommunications network to send status data less frequently based on thestatus data indicating the remaining battery life of the computingdevice.
 12. The method of claim 11, wherein the status data includeslocation data identifying the location of the computing device and isassociated with a time indicating when the status data was gathered fromthe computing device.
 13. The method of claim 11, wherein the statusdata is transmitted upon the remaining battery life associated with thecomputing device reaching a predetermined milestone.
 14. The method ofclaim 13, wherein the milestone is the remaining battery life reaching apredetermined percentage of total battery life.
 15. The method of claim13, wherein the milestone is the remaining battery life reaching apredetermined amount of remaining time left until the computing deviceruns out of battery life.
 16. A computing device comprising: one or moreprocessors; and memory containing instructions that, when executed bythe one or more processors, cause the one or more processors to performoperations comprising: receiving, by the computing device, a firstcommand over a communications network to initiate a lost mode on thecomputing device; locking the computing device or suppressing selectfunctionality of the computing device; determining a remaining batterylife of the computing device; sending, over the communications network,status data indicating at least a remaining battery life of thecomputing device, wherein the status data indicating a remaining batterylife associated with the computing device includes an estimated amountof remaining time until the computing device runs out of battery life;receiving, by the computing device, a second command to send status dataless frequently based on the status data indicating the remainingbattery life of the computing device.
 17. The computing device of claim16, wherein the status data includes location data identifying thelocation of the computing device and is associated with a timeindicating when the status data was gathered from the computing device.18. The computing device of claim 16, wherein the status data istransmitted upon the remaining battery life associated with thecomputing device reaching a predetermined milestone.
 19. The computingdevice of claim 18, wherein the milestone is the remaining battery lifereaching a predetermined percentage of total battery life.
 20. Thecomputing device of claim 18, wherein the milestone is the remainingbattery life reaching a predetermined amount of remaining time leftuntil the computing device runs out of battery life.